home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990422-19990725
/
000119_news@watsun.cc.columbia.edu _Mon May 31 14:23:35 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-07-23
|
2KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA02227
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 31 May 1999 14:23:35 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id OAA05545
for kermit.misc@watsun.cc.columbia.edu; Mon, 31 May 1999 14:11:48 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: cku195b07.sco234c crashing on reentry into server mode
Date: 31 May 1999 18:11:47 GMT
Organization: Columbia University
Message-ID: <7iujd3$5d7$1@newsmaster.cc.columbia.edu>
To: kermit.misc@watsun.cc.columbia.edu
In article <374FB6A3.83E4DAF1@squonk.net>,
Brian K. White <linut@squonk.net> wrote:
: Anyone else seeing this?
:
: hardware: 486-50, 16M ram, Digiboard PC/Xe (ISA, with 80186)
: software: Xenix 386 GT 2.3.4, digiboard driver v5.3.0, cku195b07.sco234c
: (also 195b05, will test old versions today)
:
: Recipe to get symptom:
: enter kermit
: <do any command mode operations you like, or connect as a client, all
: works ok>
: enter server mode
: <server works ok, even for long periods of uptime (tested overnight so far)>
: ctrl-c out of sever mode
: <command-mode or connect as client works ok as before>
: try to reenter server mode--->crash (detail of crash below, it doesn't
: have to crash, but will if you let it.)
:
So you are dialing out from SCO Xenix 2.3.4, and then putting the Xenix
Kermit program that dialed out into server mode?
Unfortunately I don't have access to a Xenix system from which I can dial
out to test and debug this scenario. If I did, it probably would not have
the same serial-port hardware and drivers as yours, and the same problem
might not occur.
The symptoms you describe do not resemble any other commonly occuring
problem, but we can try to track it down if you want to send in a debug
log. Please try to devise a way to reproduce this problem in a minimum
number of commands, with a minimum amount of data transfer, and then send
the resulting debug.log file to kermit-support@columbia.edu and we'll take
a look.
: btw: this reminds me of a question: is #!/usr/local/bin/kermit supposed
: to work on xenix?
:
Proper handling of "shebang" lines depends on your shell.
- Frank